Skip to content

Document boolean values in V3 Search API query value field#545

Open
kstenson wants to merge 1 commit into
mainfrom
kstenson/document-boolean-search-value
Open

Document boolean values in V3 Search API query value field#545
kstenson wants to merge 1 commit into
mainfrom
kstenson/document-boolean-search-value

Conversation

@kstenson

@kstenson kstenson commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Why?

The V3 Search API query value field accepts boolean values, but the reference only listed string, integer and array. That left a gap: filtering a boolean field with the != operator is valid, but the docs gave no indication booleans were accepted search values.

How?

Added boolean to the shared search predicate value schema and noted in its description that boolean fields accept true/false (and their string forms). The schema is shared across the conversations, contacts and tickets search endpoints, and the change is applied to every documented version.

Generated with Claude Code

The search query `value` field accepts boolean values, but the spec only
listed string, integer and array. This documents boolean as a valid search
value across all documented versions, covering the conversations, contacts
and tickets search endpoints (the schema is shared).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant